feat(project-board): decision levels and identities on the board - #1841

Verdict: PASS at 3cca5d9
Written-by: Reviewer
Attestation: 3cca5d9 role=Reviewer

Ran at this tip:

$ cd core && TZ=UTC node --test test/project-board-levels.test.js
# tests 4  # pass 4  # fail 0
$ cd core && TZ=UTC node --test test/project-board-levels.test.js test/meetings.test.js test/meetings-decide-paths.test.js test/meetings-persist.test.js test/decisions.test.js test/project-board.test.js test/project-board-view.test.js test/project-board-panels.test.js test/project-board-entry.test.js test/board-card.test.js test/no-delivery-board.test.js
# tests 92  # pass 92  # fail 0
$ node .github/scripts/changelog.mjs check
$ node scripts/ds-bot-patches.mjs check
$ node core/scripts/build-client.mjs --check
$ node .github/scripts/risk-gate.mjs --pr 1841 --repo ThinkFlowLab/FlyBot

Review (2026-10-30T15:30Z, tier T3):

• Red-first, verified on a clean tip tree: with core/src/host/meetings.js and core/src/host/project-board.js restored to their base blobs the affected suite fails at load — not ok 1 - test/project-board-levels.test.js (# tests 1 / # pass 0 / # fail 1); with the tip blobs back it is # tests 4 / # pass 4 / # fail 0. The tip blob shas were checked against the API: 513d048 meetings.js, d05ba2a host/project-board.js, 386a1a7 client/project-board.js.
• changelog.mjs check — 9 fragments well formed; ds-bot-patches check — 10 patches apply, core/ equals ds-bot/ + patches/ds-bot/; build-client.mjs --check — green (client.js matches src/client).
• Check-runs at the tip: every check terminal. Only enqueue-guard is red, with no Verifier report names the tip 3cca5d9f47d0 — the expected pre-PASS state this report answers; nothing else failed. (tests-ok, merge-gate, risk tier, package, three plugin suites, Node 24, reviewed tip, judge all green; the second agent-audience run is cancelled.)
• Scope: the compare b4e05ac…3cca5d9 is exactly the 15 files the body names — core/src/host/{meetings,project-board}.js, core/src/client/{project-board,i18n}.js, core/client.js, core/test/project-board-levels.test.js, the two subsystem docs, changelog.d fragment, and the generated patches/ds-bot mirrors. No unrelated core/ file and no patches/ds-bot/ change that is not a mirror of these sources.
• Content: level is validated against the shared CLASSES vocabulary and unknown values are refused; decide keeps a level it was not given; advanceRefusal refuses only severe and names the dissent count, so the pause reason is host truth; decisionCardOf is one exported projection used by both the read model and the test; holder/speaksFor come from task.claimedBy/task.speaksFor and are omitted when empty, so older rows render unchanged. Client renders badge, recipients, pause reason, holder and for <user> with zh keys; nothing is inferred on the client.
• Checkpoint block reads: pr 1841, claim Chief, issue 1831, summary 420 chars, 4 files all in this diff, checks.result green at the tip, whole block 1089 chars. Reviewer: Reviewer and Owner: Chief are both in the body header and name different Bots.
• Non-blocking note: patches/ds-bot/0008-client-bundle.patch was regenerated on a box without git, so its hunk headers lost their trailing section context and the diff decomposition differs from main's even though the reconstructed core/client.js changes only 34/2 lines. ds-bot-patches check is green, so the tree is consistent; it is churn to keep in mind for the next conflict in that file, not a defect.

Not run: the smoke bench (no index.js/src/host wiring change) and the full core suite beyond the 92 affected tests — this box has no git, so arch-docs cannot diff against origin/main; CI's tests-ok at this tip is green and carries the full suite.